Explore More
You have seen the whole loop; here is how the pieces fit and what else AutoMap does.
What You Just Did
The five steps map onto four ideas:
Publishing job (Steps 1 and 2) — a publication manifest: one recipe of Stationery, documents and per-target overrides that AutoMap runs on demand, on a schedule or from a pipeline
Composition job (Step 3) — assembles a site from the deployed output of its members: the shell brings the chrome, each parcel brings its content, and the combined contents are stitched from the parcels
Schedule (Step 4) — for high-velocity content, the parcel that changes every sprint
Stationery (Step 5) — the design lives there, not in the jobs, so re-pointing the jobs re-skins everything
In the trial every member had Build checked, so each composition run rebuilt all three jobs in about four minutes. In production, clear Build on the slow members and let each job publish on its own cadence: the composition then reads the deployed parcels, splices the combined contents and advances the site's cache key in seconds, without rebuilding the slow ones.
Deploy to S3 + CloudFront
The trial deploys to folders; production deploys to Amazon S3 behind CloudFront, where the 2026.1 deploy features matter. This needs an AWS account, so it is not part of the trial:
Amazon S3 destinations — Edit > Deploy Destinations... > Add > Amazon S3: Bucket URI:, Region:, Credential profile:, CloudFront distribution:; AutoMap stores no access keys, credentials come from the standard AWS credential chain
Built for caching — versioned assets are cached immutably while pages and maps are always revalidated; each deploy invalidates its own pages, and each composition advances the site's cache key in one invalidation, so a re-skin or a new parcel reaches readers without a manual cache flush
CLI & CI
Everything the Administrator runs, the command line runs headless:
"C:\Program Files\WebWorks\ePublisher\2026.1\ePublisher AutoMap\WebWorks.Automap.exe" "<your Documents folder>\WebWorks ePublisher AutoMap\Jobs\Quantum Sync Help\Quantum Sync Help.waj"Exit codes — 0 on success, 1 on errors (warnings still exit 0), so a pipeline step fails when the build fails
Flags —
-tbuilds only the named targets,-nbuilds without deploying,--skip-reports,--stagingdirDrop-in jobs — a job is a folder,
Jobs\<name>\<name>.waj, and the Administrator lists it the moment the job file lands there; a pipeline copies jobs into place with no import stepVersion control — job files are small XML with paths relative to the job and can carry their own deploy destination, as the seeded jobs do, so keep them beside the documents; ignore the
<name>-log.txtnext to each job
Scheduling Depth
Step 4 used the Windows Task Scheduler; AutoMap leans on it fully:
Run whether user is logged on or not needs the Windows user name and password (
DOMAIN\useron a domain); this is how a build server publishes unattendedLast Run Result
0x0means success and0x1errors; the Administrator shows the same as Last Result OK or ErrorJob > Suspend Job Schedule pauses a job without deleting its triggers; Resume Job Schedule brings it back
WebWorks.Automap.Administrator.restricted.batstarts the Administrator without elevation; there you can create and configure jobs but not run or schedule them (both go through Task Scheduler), so build with the command line above instead
Scripts and Build Options
Jobs can run your scripts around the build:
Job Info has Pre-build: and Post-build: scripts for the whole job, the Info tab of Target Configuration has the same pair per target, and each document group can have a Script to retrieve documents: that fetches sources first
Scripts are batch files run from the job folder, with variables for the job name and folder, the target name and output folder, and the group name; the script editor lists them
Build options on Job Info: Skip reports skips the QA reports and shortens large builds; Verbose logging (on by default) keeps step-by-step progress in the log
Try This: AI Assistant
A Reverb site can carry an AI assistant that answers questions from the site's own content. It needs a free WebWorks Platform login, and here is what to expect:
Sign in to the WebWorks Platform (free), create an assistant, and copy its Assistant ID
Select Quantum Sync Help, choose Job > Edit..., open Target Configuration, select Web Help in the target list, then the Target Settings tab; under AI Features set Generate Assistant to true, paste the ID into Assistant ID, leave Hide AI Tab when file local off, and click OK
Choose Job > Run, then Job > Preview Output in Browser > Web Help: the site has an AI tab
Ask it something. The chat returns an error, and that is expected: live answers need the output hosted on an Internet domain listed in the assistant's Origin Domains, and a local folder is not one
Try This: Custom Merge Settings
Automatic merge lists parcels as found; Custom lets you shape the combined contents:
Select Quantum Sync Site and choose Job > Edit...
Under Merge Settings choose Custom; click Add Container... and name it Quantum Sync; with the container selected, click Add Group... and add Release Notes, then again for Help (a container is a folder in the contents; only groups carry content)
Tick Also include newly published parcels not listed above, so a parcel you add later still appears after the declared ones
Click OK, choose Job > Run, and preview: Release Notes now leads, and both parcels sit under one folder in the contents
Version Control and CMS
The per-group Script to retrieve documents: is the hook for pulling sources from Git, Subversion, Perforce, Mercurial or any command-line-scriptable VCS, and from CMSs such as Vasont and SDL LiveContent. See the full documentation.
The ePublisher Product Family
| Express | Designer | AutoMap |
|---|---|---|---|
Who it's for | Authors publishing content | Teams controlling brand and design | DevOps automating builds |
What it does | Generate output from Stationery | Create and customize Stationery | CLI and scheduled builds |
Source formats | Markdown++, Word, FrameMaker, DITA | Same | Same |
Output formats | Reverb 2.0, PDF, others | Same + full skin editing | Same |
Key capability | One-click publish | Pixel-level design control | CI/CD and AI agent access |
AutoMap is the everyday publishing UI and the automation engine. To create your own Stationery, the design your jobs publish with, you need Designer: Download ePublisher Designer. ePublisher Express is the low-cost entry point for an author who only needs to publish with existing Stationery on their own desktop.